Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 29, 2026

🤖 I have created a release beep boop

1.2.0 (2026-02-02)

Features

  • add trusted origins configuration for auth (#84) (7b9c1cc)

Bug Fixes

  • prevent desktop asset and jsx runtime errors (cba616b)
  • update url env var validation (4c9014f)
  • update url env var validation (8aa4a75)

This PR was generated with Release Please. See documentation.

Greptile Overview

Greptile Summary

Automated release PR bumping version from 1.1.0 to 1.2.0. This release includes trusted origins configuration for auth, desktop asset and JSX runtime error fixes, and URL environment variable validation updates.

  • Version correctly updated in package.json, CHANGELOG.md, and .template-version.json
  • Release notes properly formatted following conventional commits
  • All version references are consistent across files

Confidence Score: 5/5

  • This PR is safe to merge - it's an automated release with consistent version updates across all files
  • This is a standard automated release PR generated by Release Please with straightforward version bumps and changelog updates. All changes are consistent and follow the expected pattern.
  • No files require special attention

Important Files Changed

Filename Overview
package.json Version bumped from 1.1.0 to 1.2.0
CHANGELOG.md Added 1.2.0 release notes with 1 feature and 3 bug fixes
.template-version.json Template version updated from 1.1.0 to 1.2.0

Sequence Diagram

sequenceDiagram
    participant ReleaseBot as Release Please Bot
    participant package as package.json
    participant changelog as CHANGELOG.md
    participant template as .template-version.json
    
    ReleaseBot->>package: Update version 1.1.0 → 1.2.0
    ReleaseBot->>changelog: Add 1.2.0 release notes
    Note over changelog: Features: trusted origins config<br/>Bug Fixes: desktop assets, url validation
    ReleaseBot->>template: Update version 1.1.0 → 1.2.0
    
    Note over ReleaseBot,template: All version updates synchronized
Loading

@coderabbitai
Copy link

coderabbitai bot commented Jan 29, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--init branch 9 times, most recently from cbf183d to e9517ef Compare February 1, 2026 19:45
Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

Comment on lines +8 to +15
* prevent desktop asset and jsx runtime errors ([cba616b](https://github.com/metaideas/init/commit/cba616b547b0df13b6cc5f9529c9964c176b885b))
* update url env var validation ([4c9014f](https://github.com/metaideas/init/commit/4c9014f98db496b16cba47dccd8d034b5a214160))
* update url env var validation ([8aa4a75](https://github.com/metaideas/init/commit/8aa4a752a41d5c9af783e4c1c15ab9bcb99d3662))
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] The 1.1.1 changelog lists the same bullet title twice (update url env var validation) with different commit SHAs. If this is the same fix cherry-picked/reverted/reapplied, it may be worth consolidating into a single entry to avoid confusing release notes.

Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 8:10

Comment:
[P2] The 1.1.1 changelog lists the same bullet title twice (`update url env var validation`) with different commit SHAs. If this is the same fix cherry-picked/reverted/reapplied, it may be worth consolidating into a single entry to avoid confusing release notes.

How can I resolve this? If you propose a fix, please make it concise.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--init branch from e9517ef to 6e75581 Compare February 1, 2026 19:46
@github-actions github-actions bot changed the title chore(main): release init 1.1.1 chore(main): release init 1.2.0 Feb 1, 2026
@github-actions github-actions bot force-pushed the release-please--branches--main--components--init branch from 6e75581 to e9af40c Compare February 1, 2026 20:14
@github-actions github-actions bot force-pushed the release-please--branches--main--components--init branch from e9af40c to 01e7d6f Compare February 2, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants